Network-layer and link-layer use of shadow addresses in soft handoff within subnets

ABSTRACT

A technique for assigning an address (“shadow address”) to a mobile station that is compatible with the layer-2 address on the wireline network which serves the mobile station. The shadow address is then used as a wireline identifier for the destination address for frames ultimately destined for the mobile station. The shadow address is stored in a watch list for serving base stations, and any base station receiving a frame with a shadow address in its watch list process the frame to forward it the to mobile station. In this way, the shadow address facilitates carrying out soft handoff and smooth handoff.

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application is a non-provisional application of provisionalapplication Serial No. 60/280,298 filed Mar. 30, 2001.

BACKGROUND OF THE DISCLOSURE

[0002] 1. Field of the Invention

[0003] This invention relates generally to a wireless-to-wireline andwireless-to-wireless communication system that is composed of wirelessaccess networks interconnected via a wireline IP (Internet Protocol)network, and, more particularly, to methodologies and concomitantcircuitry for effecting soft handoff in the wireless portion of thesystem.

[0004] 2. Description of the Background Art

[0005] Today, many different wireless systems exist, ranging from indoorwireless LANs (Local Area Networks) to outdoor cellular systems.Generally, the numerous wireless systems are not compatible with eachother, making it difficult to roam from one system to another. Althoughthere have been attempts to unify third-generation wireless systems,incompatible systems are expected to co-exist in the future.Furthermore, wireless LANs and cellular wireless systems are beingdeveloped independently, and such systems are also evolvingindependently. So far, no wireless technology has emerged as a commonand long-term universal solution.

[0006] IP (Internet Protocol), which is already a universalnetwork-layer protocol for packet networks, is rapidly becoming apromising universal network-layer protocol for wireless systems. An IPterminal, with multiple radio interfaces, can roam between differentwireless systems if they all support IP as a common network layer.Unlike today's wireless systems in which Radio Access Networks (RANs)are mostly proprietary, IP provides an open interface and promotes anopen market. IP will also enable widely adopted and rapidly growingIP-based applications to run over wireless networks. Moreover,distributed, autonomous IP-based wireless base stations have thepotential of making the wireless systems more robust, scalable, and costeffective.

[0007] There are, however, many challenges to realizing distributedall-IP wireless networks. For the sake of specificity in discussingthese challenges as well as pointing out problem areas, reference ismade to FIG. 1. The depiction of network 100 in FIG. 1 illustrates anexemplary configuration of a network that uses IP-based wireless basestations (designated iBSs). The coverage area of the wireless network isdefined by a multiplicity of cells (e.g., cells 101, 102, 103). Thegeographical area covered by each wireless base station is referred toas a cell (e.g., iBS 111 serves cell 101, and so forth). When mobilestation 104 moves from one cell (e.g., cell 101 originally) into theoverlapping regions (e.g., overlap of cells 101 and 102) of the coverageareas of multiple base stations, base station 111 may perform a“handoff” of mobile station 104 to base station 112. Handoff is aprocess whereby a mobile station communicating with one wireless basestation is switched to another base station during a session. Overlapregions 117 and 118 are coverage areas where handoff is effected. Forexample, as mobile station 104 moves into region 117 while roaming incell 101, the radio signal strength from iBS 2 (depicted by referencenumeral 115) may be greater than the radio signal strength (114) fromiBS 1, so handoff is warranted to maintain the quality of theestablished session.

[0008] Among the key challenges in a distributed all-IP wireless networkis how to support “soft handoff”. As suggested above, handoff is theprocess that allows a mobile station's session-in-progress to continuewithout interruption when a mobile station (MS) moves from one wirelesscell to another. Soft handoff is a form of handoff whereby a mobilestation can start communication with the target base stations withoutinterrupting the communication with the serving base station. Thus, softhandoff allows a MS to communicate with multiple base stations (BSs)simultaneously. In particular, soft handoff has been shown to be aneffective way for increasing the capacity, reliability, and coveragerange of CDMA-based wireless networks. Soft handoff also provides moretime for carrying out the handoff procedure.

[0009] Soft handoff in a CDMA-based wireless system is the focus of thesubject matter of the present invention. In Code Division MultipleAccess (CDMA) radio systems, a narrowband user message signal ismultiplied by a very large bandwidth signal called the spreading signal.The spreading signal is a pseudo-noise code sequence that has acommunication signal rate which is orders of magnitudes greater than thedata rate of the user message signal. All users in a CDMA system maytransmit simultaneously. Each user has its own pseudorandom code forcoding its own message signal—each code is approximately orthogonal toall other codes. A receiver is assigned a code to detect a desired usermessage signal, and performs a time correlation operation to detect onlythe specific assigned code. All other codes appear as noise due tode-correlation. CDMA is effective in wireless systems because a receivercan be assigned a multiplicity of codes to detect message signals from acorresponding multiplicity of transmitters, thereby engendering the softhandoff process.

[0010] An IP router is an IP network device that runs IP layer routingprotocol (e.g., OSPF and BGP) and forwards IP packets. The running of arouting protocol decides the “routing policy”, and the forwarding of IPpackets realizes the “routing mechanism”. IP packets arriving from thewireline IP network (121) at a given base station (e.g., iBS 111 overwireline path 122 or iBS 112 over path 123) can be routed by the routingmechanism of the base station to mobile station 104 (or otherappropriate wireline devices that connect directly to the base station).

[0011] Today, the only known approach to designing an IP-based basestation is to add (or connect) radio transmission and receivingequipment directly onto an IP router (131). Such a design, however, hasa potentially serious shortcoming. In particular, the mobile stationsserved by different base stations must belong to different IP subnets,that is, the design forces the mobile stations in different cells to beon different IP subnets. (Here, a subnet is used in the sense defined byan IP address, which has the form, for example, “w.x.y.z” (e.g.,129.3.2.14), wherein “w.x” is the network address (129.3), “y” (2) isthe subnet address for a device associated with the given network, and“z” (14) is the host address for a device associated with the givennetwork/subnet, such as a mobile terminal or a base station. In terms ofFIG. 1, iBS 1 may be assigned the subnet address 2, whereas mobilestation 104 may have the host address 14.) Suppose, for the sake ofargument, that a mobile station is served by two base stations belongingto the same IP subnet S. Then, both iBSs (IP routers) will advertise toother routers in the overall network that they can reach all the hostson subnet S. However, each iBS can only reach a subset of the hosts onsubnet S (i.e., the set of hosts being currently served by the basestation). This means that other routers will not be able to determinewhich base station should receive a packet destined for a host on subnetS. In other words, packets may be delivered to the wrong base stationand consequently cannot reach the destined host.

[0012] The fact that mobile stations (MSs) in different cells belong todifferent IP subnets suggests that an MS may have to change its IPaddress every time it moves into a new cell. Changing IP address usuallytakes a long time using today's methods for dynamic IP addressassignment (e.g., the Dynamic Host Configuration Protocol or DHCP). Whencertain IP-layer mobility management mechanisms are used (e.g.,SIP-based mobility management), a change of IP address can also meanthat the old session may need to be modified, or new SIP sessions mayhave to be established.

[0013] Having to change IP addresses when moving from one cell toanother also makes soft handoff more difficult to implement. Forexample, if an MS has to use different IP addresses to receive IPpackets from different iBSs, IP packets coming to the MS from differentiBSs will not be identical because they carry different IP destinationaddresses. Consequently, copies of the same packets from different basestations may not be correctly combined by the MS's radio system.

[0014] Recently, methods (e.g., HAWAII, Cellular IP) have been proposedto enable MSs to move within a domain of multiple IP subnets withouthaving to change their IP addresses. These methods, however, typicallyrequire complex IP-layer signaling and significant changes to the IProuters in the domain. Furthermore, these methods have not consideredhow to solve the data content synchronization problem.

[0015] From another viewpoint, in today's circuit-switched CDMA networkssuch as IS-95, a centralized Selection and Distribution Unit (SDU) isresponsible for data distribution in the forward direction (from BS toMS). The SDU creates and distributes multiple streams of the same dataover layer-2 circuits to multiple BSs that in turn relay the data to theMS. The MS's radio system (typically working below the IP layer)collaborates with the BSs to synchronize the radio channel frames andcombine the radio signals received from different BSs to generate asingle final copy of received data. The SDU helps ensure data contentsynchronization by ensuring that the matching layer-2 frames sent todifferent base stations contain copies of the same data. In the reversedirection (from MS to BS), the MS ensures that the matching layer-2frames sent to different BSs contain copies of the same data. The SDUthen selects one of the frames received from different base stations asthe final copy of the data.

[0016] Accordingly, as evidenced by the foregoing discussion, achievingsoft handoff among distributed iBSs introduces several new technicalproblems that cannot be solved readily by the mechanisms developed fortoday's centralized circuit-switched wireless networks.

[0017] One problem already alluded to is loss of data contentsynchronization. With distributed iBSs, centralized control entities,such as the SDU in circuit switched wireless networks, will no longerexist. Consequently, even though the CDMA radio system is capable ofsynchronizing the link and physical layer frames on the radio channel,it cannot, on its own, guarantee that the matching frames from differentbase stations will carry copies of the same data. For example, IPpackets can be lost on their way to the MS, creating random gaps in thepacket streams received by the MS from different iBSs. Furthermore,copies of the same data may arrive at the MS at different times due tothe random delays suffered by the packets. Random gaps and delays canlead to a loss of data content synchronization. Suppose that packet X islost at iBS 1 (due to, for example, buffer overflow) but is not lost atiBS 2. Then, another totally unrelated packet Y from iBS 1 and packet Xfrom iBS 2 may arrive at the MS at the same time and the MS's radiosystem will not be able to tell that they are not copies of the samedata and will hence erroneously combine X with Y.

[0018] Another problem is how to support soft handoff, which requires amobile station to receive identical copies of the same data frommultiple base stations simultaneously. When the mobile stations servedby different base stations belong to different IP subnets, complexIP-layer signaling capabilities (e.g., IP multicast) have conventionallybe required to direct copies of the same IP packets via multiple basestations to the mobile station. Furthermore, copies of the same IPpacket arriving from different base stations to the mobile station willnot be identical because these packets will carry different destinationIP addresses. This makes it impossible for the mobile station's radiosystem to combine the signals from different base stations into a singlecopy of data.

[0019] The art is devoid of a methodology and concomitant systems thateffect soft handoff in an all-IP wireless network that uses autonomousiBSs in a configuration having the following characteristics thatdifferentiate the configuration from existing wireless networks: (a) theiBSs use IP protocols for both signaling and transport of user traffic.For example, they may route/forward IP packets based on informationcarried in the IP headers, perform IP-layer signaling, mobilitymanagement and Quality of Service (QoS) management functions; (b) theiBSs function autonomously. There is no centralized signaling andcontrol over the behaviors of the iBSs; (c) the iBSs are interconnectedvia an IP network which could have arbitrary network topology such asbus, ring, star, tree, etc.; and (d) the cells (a cell is a geographicalradio coverage area of a BS) can be arranged in any arbitraryconfiguration.

SUMMARY OF THE INVENTION

[0020] These shortcomings and other limitations and deficiencies areobviated, in accordance with the present invention, by assigning analias or shadow address to a mobile station that is compatible with thelink layer address of the wireline subnet which delivers packets to themobile station via base stations connected to the wireline subnet,storing the shadow address in the base stations that serve the mobilestation during soft handoff, and using the shadow address of the mobilestation for packets communicated to the mobile station via the basestations from a sending device coupled to the subnet.

[0021] Broadly, in accordance with a method aspect of the presentinvention, a method for carrying out soft handoff of a mobile stationfrom a first base station to a second base station both served by awireline subnet having a link layer different than the link layer of thewireless network serving the mobile station, includes: (a) storing ashadow address in the first base station and the second base station,the shadow address corresponding to the mobile station and having aformat compatible with the link layer of the wireline subnet; (b)transmitting a frame containing the packet from the sending device overthe wireline subnet using the shadow address as the link layerdestination address of the packet; and (c) concurrently processing theframe received from the first base station and the second base stationin the mobile station.

[0022] Broadly, in accordance with a system aspect of the presentinvention, circuitry for carrying out soft handoff of a mobile stationfrom a first base station to a second base station both served by awireline subnet having a link layer different than the link layer of thewireless network serving the mobile station, includes: (a) a storagedevice for storing a shadow address in the first base station and thesecond base station, the shadow address corresponding to the mobilestation and having a format compatible with the link layer of thewireline subnet; (b) a receiver for receiving a frame containing thepacket transmitted from the sending device over the wireline subnet toboth the first base station and the second base station using the shadowaddress as the link layer destination address of the packet; (c) aprocessor for concurrently processing the frame as receive from thefirst base station and the frame as received from the second basestation in the mobile station, and (d) copies of the same IP packet canbe relayed by multiple IP-based base stations to the same mobile stationwithout requiring the sending device to be modified to support thiscapability.

[0023] The features in accordance with the present invention include:(a) mobile stations served by multiple IP-based base stations can be onthe same IP subnet. This ability reduces the need for a mobile stationto change its IP address when moving into a new cell; (b) copies of thesame IP packet to be relayed by multiple IP-based base stations to thesame mobile station without any IP-layer signaling or any othersignaling above the IP layer. This capability makes it easier to achievesoft handoff between IP-based base stations because one requirement ofsoft handoff is that multiple base stations can relay simultaneouslycopies of the same data to the mobile station; and (c) copies of thesame IP packet can be relayed by multiple IP-based base stations to thesame mobile station without requiring the mobile station to use morethan one IP address simultaneously. This capability further simplifiessoft handoff implementation and reduces stringent requirements on mobilestations.

BRIEF DESCRIPTION OF THE DRAWING

[0024] The teachings of the present invention can be readily understoodby considering the following detailed description in conjunction withthe accompanying drawings, in which:

[0025]FIG. 1 depicts a wireline-wireless system composed of autonomousbase stations serving mobile stations;

[0026]FIG. 2 depicts a system composed of both wireline and wirelessnetworks wherein base stations on a subnet serve mobile stations usingtheir shadow addresses;

[0027]FIGS. 3A and 3B depict a generic IP packet and an IP packet havinga mobile station as a destination device, respectively;

[0028]FIGS. 3C and 3D depict a generic Ethernet frame and an Ethernetframe having the shadow address of the mobile station as an Ethernetdestination address, respectively;

[0029]FIG. 4 depicts a system composed of both wireline and wirelessnetworks wherein a multiplicity of base stations on the same subnet sendmultiple copies of a packet to a roaming mobile station to carry outsoft handoff;

[0030]FIG. 5 depicts base station processing in terms of conventionalphysical layer, link layer, and IP layer protocol stacks while usingshadow addresses of mobile stations;

[0031]FIG. 6 depicts the arrangement of a base station in terms of onlythe conventional physical layer and link layer protocol stacks toprocess shadow addresses of mobile stations;

[0032]FIG. 7 depicts the processing by a base station that performs therouting mechanism without changing the routing policy fostered by shadowaddresses;

[0033]FIG. 8 is a flow diagram depicting the process of assigning ashadow address to a mobile station;

[0034]FIG. 9 is a flow diagram depicting the process by which a mobilestation associates with a new base station using physical layerinformation and link layer messages;

[0035]FIG. 10 is a flow diagram depicting the process of assigning ashadow address by a base station upon first power-up of a mobilestation;

[0036]FIG. 11 is a flow diagram depicting the process of assigning ashadow address by a candidate base station for a powered-up mobilestation handled by a serving base station;

[0037]FIG. 12 is a flow diagram depicting the process of deleting ashadow address from a watch list;

[0038]FIG. 13 is a pictorial representation of a mobile station roamingfrom one cellular region served by one subnet to another cellular regionserved by another subnet during the process of soft handoff;

[0039]FIG. 14 is a flow diagram depicting an illustrative technique forgenerating entries for the Packet Duplication table, including amultiplicity of IP layer address associated with a roaming mobilestation

[0040]FIG. 15 is a time diagram depicting the time relationship ofpackets and frames as delivered by two base stations to a mobilereceiver involved in soft handoff across subnets;

[0041]FIG. 16 is a pictorial representation illustrating recovery ofsynchronization for matchable packet streams during soft handoff; and

[0042]FIG. 17 is a flow diagram depicting the algorithm to regainsynchronization for matchable packet streams during soft handoff.

DETAILED DESCRIPTION

[0043] 1. Soft Handoff Within a Subnet

[0044] 1.1. “Shadow” Address

[0045] As illustrated by system 200 in FIG. 2, which is a recast versionof system 100 of FIG. 1 for purposes of highlighting the principles ofthe present invention, on one side of iBS 1 and iBS 2 (111 and 112,respectively) is wireline IP network 201. Wireline IP network 201 servesas one subnet used to interconnect iBS 1 and iBS 2 with router 131. Forsake of specificity, but without loss of generality, wireline IP network201 is presumed to be an Ethernet. Router 131 is also coupled to otherIP networks, such as the Internet, via another port to deliver packetsto and from wireline IP network 201 over path 132. On the other side ofiBS 1 and iBS 2 is a wireless network represented, in part, by wirelessradio path 114 linking MS 104 with iBS 1. Thus, there is a cleardemarcation between the wireline and wireless aspects of system 200,which is depicted in FIG. 2 by the Ethernet and non-Ethernet portions ofsystem 200.

[0046] It is also readily appreciated that, whereas the sending devicewas exemplified as being coupled, for example, into wireline network 201from a device propagating a packet through router 131 of FIG. 2, it isclear that the principles of the present invention also apply for awireless sending device that use a link layer addressing scheme which iscompatible with the link layer of the subnet. Accordingly, both casesare covered in the description by stating that the sending device is“coupled to” the wireline subnet, thereby covering (but not beinglimited to) both direct connection or wireless coupling to the subnet.

[0047] To understand the importance of the separation between thewireline and wireless sides of the base stations, consider theramifications of a single IP subnet serving multiple iBSs, asillustrated in FIG. 2. Generically, when a device (e.g., router, iBS, orhost) on the wireline IP subnet wants to send an IP packet to a mobilestation, the sending device, by convention, normally determines thelayer-2 address that should be used to send the IP packet over thewireline subnet to the base station handling the mobile station. But,when the mobile station is using a different layer-2 protocol that isincompatible with the layer-2 protocol used on the wireline subnet, thesending device cannot use the layer-2 address of the mobile to send IPpackets over the wireline subnet. This will be the case, for example,when the wireless network uses CDMA technologies that have a differentformat for the layer-2 address than that on the wireline subnet (such asEthernet).

[0048] To circumvent this difficulty and to ensure that a sending devicecan direct the packet to the right base station, consider firstdeploying the wireline layer-2 address (e.g., MAC address in the case ofEthernet) of the destination base station as an alias for the mobilestation and, accordingly, the sending device would forward the packet tothe destination base station as the proxy for the mobile station. Then,the base station can use, in turn, IP-layer and/or other layerinformation to determine to which mobile station the packet should besent. This is only part of the solution, however, because in thisscenario only a single base station serves the mobile station. To carryout soft handoff, it is necessary that multiple base stations relaycopies of the same packet to the mobile station which would be difficultin the above scenario, that is, sending a packet to only a single basestation's wireline layer 2 address.

[0049] Consider now an extension to the above approach whereby aso-called “shadow address” is utilized. With the shadow addressapproach, besides the unique wireless layer-2 address normally allocatedto each mobile station, a unique wireline layer-2 address is alsoassigned to the mobile station. Since the mobile station may be using adifferent layer 2 than the wireline network, the wireline layer-2address assigned to the mobile station may have no meaning to the mobilestation and cannot be used by the mobile station for any other purposes.However, the wireline layer-2 address assigned to the mobile station canbe advantageously used by a base station to determine which layer-2frame arriving from the wireline network should be accepted by the basestation and, if accepted, to pass the IP packet contained in the layer-2frame to the IP layer in the base station for further processing. The IPlayer of the base station then uses the information in the IP header ofthe incoming IP packet to determine which radio interface on the basestation the packet should be sent to. In essence, the wireline layer-2address assigned to a mobile station can be viewed as a “shadow” thatthe mobile station casts on the wireline layer 2. For this reason, thewireline layer-2 address assigned to a mobile station will be referredto as the shadow wireline layer-2 address of the mobile station, or“shadow address” for short.

[0050] Each base station maintains a “watch list” similar to that inTable 1. The field denoted “MS's IP Address” contains the IP addresswhich is assigned to the mobile station in the subnet. The field denoted“MS's Shadow Address” is the shadow wireline layer-2 address. Table 1shows the address in the format of the IEEE 802.3 MAC address which isthe most popular link layer or layer 2 for a LAN (layer 2 and link layerare used interchangeably in the sequel without loss of generality). Thefield denoted “MS's Link Layer Address” is the real wireless link layeraddress of the mobile station. It could be the link layer address forany one of many different standards, such as cdma2000, WCDMA, Bluetooth,and so forth. TABLE 1 MS's IP Address MS's Shadow Address MS's LinkLayer Address 128.33.22.121 00:60:1D:03:E7:E1 xxxxxx 129.55.32.131E1:E7:03:1D:60:01 yyyyyy . . . . . . . . . . . . . . . . . .

[0051] The shadow address may be assigned to a mobile stationdynamically when the mobile station powers up and accesses the wirelessnetwork for the first time. Or, it can be configured in the mobilestation prior to the first time it is powered, that is, each mobilestation may be assigned a shadow address in addition to a real linklayer address. Shadow address assignment will be discussed in moredetail below when flow diagrams are presented.

[0052] 1.2. Use of Shadow Address by a Base Station to Relay a Packet

[0053] Each base station uses the shadow address created for each mobilestation to help relay an IP packet between the wireless and the wirelinenetworks. The wireline interface of each base station examines thelayer-2 destination address of each layer-2 frame arriving from thewireline network. If the destination layer-2 address matches any shadowaddress in its watch list, the base station accepts the frame, takes theIP packet out from the frame, and passes the IP packet to the basestation's IP layer for further processing. For ease of discussion, theterm “matching frames” is used to refer to a layer-2 frame whosedestination layer-2 address matches one of the shadow addressescurrently in the base station's watch list. If the IP packet is destinedfor one of the mobile stations currently served by the base station, theIP layer forwards the IP packet to the destination mobile station. Ifthe IP packet is not destined for either any mobile station currentlybeing served by the base station or the base station itself, the IPlayer may ignore the packet.

[0054] When any device on the local wireline IP subnet wants to send afirst IP packet to a mobile station, the sending device must firstdetermine the shadow wireline layer-2 address of the destination mobilestation. The sending device can do this, for example, by using thewell-known, conventional Address Resolution Protocol (ARP) designed forthe wireline IP network. In particular, the sending device willbroadcast an ARP REQUEST packet over the local IP subnet. The basestation that has the shadow layer-2 address of the destination mobilestation in its watch list will respond to the ARP REQUEST with theshadow layer-2 address of the destination mobile station. The shadowwireline layer-2 address will then be used by the sending device on thelocal IP wireline network to send a packet to the mobile station via thebase station responding to the ARP REQUEST. In addition, when the shadowlayer-2 address of a destination mobile station is in the watch list ofmultiple base stations, all of the base stations may respond to the ARPREQUEST. These responses will contain the same shadow address of thedestination mobile station. The import of multiple base stations havingthe mobile station on their watch lists will be elaborated upon shortly.

[0055] To illustrate the foregoing discussion concretely, consider theIP packet of FIG. 3A composed generally an IP payload 303 and an IPheader which is composed of, among other information, the IP destinationaddress 301 and IP source address 302. In addition, suppose the packetis originated by an IP sending device coupled to path 132 of FIG. 2, andthe packet is destined for mobile station 104 served by iBS 1. Thus, theIP destination address is the IP address of the mobile station 104—thisparticular packet is shown in FIG. 3B. In order for the sending deviceto decide how to encapsulate the packet at layer 2, the sending devicepropagates an ARP REQUEST asking for the layer-2 address thatcorresponds to the IP address of the mobile station (e.g. 128.33.22.121in Table 1) over wireline IP network 201, which again for concreteness,is presumed to be an Ethernet. The ARP REQUEST reaches iBS 1, and iBS 1notes that this IP address is in its watch list and it is associatedwith mobile station 104. In response to the ARP REQUEST, iBS 1 sends theshadow address (00:60:1D:03:E7:E1) of mobile station 104 to the sendingdevice. The shadow address, which is an actual wireline layer-2 addressfor wireline 201, can then be used by the sending device to encapsulatethe packet into an Ethernet frame. A generic Ethernet frame is shown inFIG. 3C and has, besides the packet fields, the Ethernet destinationaddress 311 and the Ethernet source address 312. In FIG. 3D, the actualEthernet frame containing the given packet is shown; the Ethernetdestination address is the shadow address of mobile station 104.

[0056] As the Ethernet frame of FIG. 3D propagates over wireline 201,the frame is detected by iBS 1. Then iBS 1, via its watch list,recognizes the shadow address in the Ethernet frame as one being servedby iBS 1. Accordingly, iBS 1 handles the Ethernet frame by stripping offthe layer-2 information, including fields 311 and 312, and passes the IPpacket to the IP layer processing of iBS 1. Processing at the IP layerwill be discussed in more detail in the sequel.

[0057] The layer-2 frames going out from a base station to the wirelineIP network may set its source layer-2 address to the shadow layer-2address of the source mobile station (the mobile station that originatedthis packet) or the layer-2 address of the base station.

[0058] 1.3. Base Stations Use of Shadow Addresses to SimultaneouslyRelay Copies of the Same Packet to a Mobile in Soft Handoff State

[0059] Arrangement 400 of FIG. 4 illustrates how multiple base stationscan use the shadow layer-2 address of a mobile station to simultaneouslyrelay copies of the same IP packet to the mobile station to carry outsoft handoff.

[0060] Suppose initially that mobile station 104 is registered with iBS1 (111), and that mobile station (MS) 104 has the parameters listed inrow 1 of Table 1 above, that is, the IP address of the MS 104 is128.33.22.121 and the shadow address is 00:60:1D:03:E7:E1 (which will becalled MAC₁₀₄ for short). Watch list 1 (401) in iBS 1 is, forillustrative purposes, that exemplified by Table 1; accordingly, theshadow address of MS 104 is in watch list 401. When mobile station 104first starts communication with new base station iBS 2 (112) as it roamsinto the overlap of the cellular regions, iBS 2 will insert MAC₁₀₄ intoits watch list, shown as watch list 2 (402). Many ways exist for the newbase station to learn the shadow address of the MS and will be discussedin greater detail later. Exemplary contents for watch list 402 arelisted in Table 2 below; the third row contains information about MS104. From this point in time, iBS 2 will accept a layer-2 frame comingfrom the wireline network that carries MAC₁₀₄ as the destination layer-2address and will send the packet carried in this frame to the IP layeron iBS 2 for further processing. TABLE 2 MS's IP Address MS's ShadowAddress MS's Link Layer Address . . . . . . . . . 128.44.12.111F1:F7:04:2D:70:03 zzzzzzzzz 128.33.22.121 00:60:1D:03:E7:E1 xxxxxx . . .. . . . . .

[0061] Since both base stations iBS 1 and iBS 2 now have MAC₁₀₄ in theirwatch lists, they will both accept layer-2 frames destined for MAC₁₀₄and forward the IP packet carried in these frames to the mobile stationsimultaneously, as exemplified by path 405 and path 406, respectively.Path 405 delivers Ethernet frame 404 containing MAC₁₀₄ and an embeddedIP packet over IP subnet 201 to iBS 1 and, in turn, over a radio channelto MS 104. Similarly, path 406 delivers IP frame 404 containing MAC₁₀₄and the embedded IP packet over IP subnet 201 to iBS 2 and, in turn,over a radio channel to MS 104.

[0062]FIG. 5 illustrates the arrangement 500 of a base station in termsof conventional protocol stacks, namely, physical layers 501-1 and501-2, link or layer 2 layers 502-1 and 502-2 (e.g., receiving frames),and the IP layers 503 (e.g., receiving packets) to process the shadowwireline layer-2 address for a mobile station. Layers 501-1 and 502-1are associated with the wireline side of the base station, whereaslayers 501-2 and 502-2 are associated with the wireless side of the basestation. By way of reiteration, the main purpose of shadow addresses isto enable the wireline interface of the base station to accept thelayer-2 frames that arrive from wireline networks and are destined formobile stations served currently by the base station with reference toits watch list. The wireline interface of the base station will monitorall layer-2 frames that come from the wireline network and will acceptany layer-2 frame whose destination layer-2 address matches the shadowaddress of any mobile station currently being served by the basestation. As depicted in FIG. 5, there are two incoming frames labeled511 and 521, respectively. It is presumed that only frame 512 has alayer-2 destination address that is in the watch list (505) for the basestation. In effect, the watch list acts as a filter to select only thoseframes having a destination address which is either the base stationlayer 2 address or shadow addresses contained in the watch list. Once alayer-2 frame is accepted by the wireline layer 2, the IP packet (522-1)carried in the frame will be extracted and passed to the IP layerforwarding engine 506 in IP layer 503 for any processing (e.g., QoScontrol) at the IP layer.

[0063] In particular, the IP address of the mobile station is known tothe base station via, for instance, the contents of watch listexemplified by Table 1. Moreover, the base station utilizes anothertable that maps radio channels to mobile stations; an illustrative tableis shown by Table 3: TABLE 3 Radio Channel Number MS's IP Address MS'sLink Layer Address 1 not assigned . . . 2 128.33.22.121 xxxxxx . . . . .. . . . N 129.55.32.131 yyyyyy

[0064] The IP address of mobile station 104, as used throughout thediscussion, is on the second row of Table 3, namely, 128.33.22.121.Radio channel 2 is presently serving mobile station 104. Outgoing packet522-2 from the IP forwarding engine, which is the counterpart toincoming packet 522-1 resulting from processing in IP forwarding engine506, is passed to layer 2 (502-2) for encapsulation. The frame format isthat deployed by the radio system, and the destination address isdetermined from the mobile station's layer-2 address from watch list505. Finally, the layer 2 radio frame is propagated to mobile station104 over wireless channel 114.

[0065] A base station could also directly use the shadow addresses todetermine to which mobile station a layer-2 frame arriving from thewireline network should be sent to and then send the layer-2 framedirectly to the outgoing radio channel without IP-layer processing. Thisprocess is referred to as layer-2 switching, which means switchinglayer-2 frames from an incoming layer 2 to an outgoing layer 2 of a basestation. In this mode, the base station is essentially functioning as alayer-2 bridge.

[0066] The arrangement 600 of FIG. 6 depicts this scenario. As in FIG.5, an incoming frame is passed to layer 2 (501-2) whenever the layer-2address of the incoming frame is in the watch list. Because the watchlist has the necessary information to complete packet forwarding atlayer 2, namely, the layer-2 wireline address (e.g., xxxxxx), the IPlayer processing can be bypassed if desired. Again, the contents ofTable 3 can be use to identify the mobile station by its layer 2 address(606), and encapsulate the frame propagated by radio channel 531 usingthe layer-2 wireless address (it is clear that a simplified version ofTable 3 is possible in this case, wherein only the first and thirdcolumns compose the simplified table). Note that the base stationswitches the payload of the incoming frame (e.g., IP packets in case ofIP-based base station) rather than the entire incoming layer-2 frame.This is because wireless and wireline layer-2 protocols used in thenetwork can be completely different and, consequently, the layer-2header on the wireline network will become useless in the wirelessnetwork and vice versa.

[0067] 1.4. IP-Based Base Station Performs Routing Mechanism withoutChanging Routing Policy

[0068] One operational principle in accordance with the presentinvention is that each IP-based base station will act as an IP-layerforwarder, as alluded to in FIG. 5. Now referring to FIG. 7, there isshown a pictorial representation of the processing effected by a basestation so that the routing mechanism based on shadow addresses does notrequire a change in the routing policy of a base station. In particular,in one operational mode, iBS 701 (representative of, say iBS 1 (111))uses the information in the IP header of an incoming packet (e.g., IP 0)from wireline interface 722 and a routing table to determine where thepacket should be sent, and then forwards the packets to the correctoutgoing radio channel, i.e. iBS 701 station performs the IP routingmechanism. However, it is not required that a base station run IProuting protocols to change its routing table. For instance, IPforwarding engine 707 may determine that IP 0 is bound for MS 1 (711)and, accordingly, forwards IP 0 as outbound packet IP 1 to MS 1 viaelectronic/radio path 715 in radio interface 721 and radio path 713. Adescription similar to the above also applies to MS 2 (712).

[0069] 1.5. Assignment and Processing of Shadow Addresses

[0070] There exist many ways for a new base station to learn about orassign the shadow address for a MS. For example, the iBSs may obtain theshadow address for a MS from a network server responsible for assigningshadow addresses. Alternatively, and the focus in accordance with thepresent invention, is the case wherein the iBSs themselves can beresponsible for assigning shadow addresses to MSs. In this case, the MSmay carry its own shadow address and pass it along to the new basestation or the new base station may obtain a MS's shadow address fromthe serving base station

[0071] By way of elucidating the details of a representative techniquefor assigning and using a shadow address which illustrates themethodology whereby the MS carries its shadow address, it is assumed inthe following description that: the serving iBS assigns a shadow addressto a MS; the MS passes its assigned shadow address to a new iBS; andwhen a MS's shadow address conflicts with any shadow address currentlyin use in the new cell, the new iBS will negotiate with the serving iBSto resolve the conflict.

[0072] An illustrative technique for assigning a shadow address to amobile station by the iBS is depicted by flow diagram 800 of FIG. 8. Theprocess starts with processing block 805 when the MS is powered up in awireless region. Next, as evidenced by processing block 810, the MSscans to locate a candidate iBS to serve the MS based upon the value ofthe signal-to-noise ratio (SNR) using a so-called “scanning algorithm”(the scanning algorithm is conventional to a mobile service environment,and it is carried out at the “physical” layer level). Once a candidateiBS is located, processing by block 815 is invoked whereby the MS sendsa “request to associate” with the candidate iBS; the request includesthe MS identifier (as described below) which is unique to the MS. Next,via processing block 820, the candidate iBS assigns a shadow address tothe MS which is compatible with the wireline link layer of the subnet towhich the iBS is connected. The MS may also need to obtain an IP addressif it does not already have one (e.g., when the MS tries to use IPservices for the first time) or if it needs a new IP address (e.g., whenit moves into a new IP subnet). The MS may use any existing methods(e.g., DHCP) to obtain an IP address. In terms of the example used tofill the second row of Table 2, the IP address assigned is 128.44.12.111and the shadow address assigned is F1:F7:04:2D:70:03. Processing block825 is executed so that the candidate iBS stores the shadow address, IPaddress, and the wireless link layer address of the MS in the watch listand the candidate iBS becomes the serving iBS. Finally, as perprocessing block 830, the MS stores the IP address and the shadowaddress to be used during packet processing, as discussed in more detaillater.

[0073] In the foregoing the term MS identifier was used, and thefollowing is a brief description of one realization of such anidentifier. A wireless network interface card (NIC) of a MS is assigneda unique address by the manufacturer of the particular NIC—this addressis called the “MS MAC address” or, equivalently, the “MS identifier”,where MAC is the acronym for Medium Access Control; the MAC Address isutilized at the “link” layer in the wireless network portion of awireline/wireless network. Each MS identifier usually has 48 bits whichcan be formatted as follows: “B1:B2:B3:B4:B5:B6”, where B 1, B2, . . .is each one byte. Also, since each byte can be treated as containing two4-bit nibbles, the MS identifier is such that each nibble can beexpressed in hexadecimal. Thus, a typical MS identifier might be:“18:00:20:E8:42:F6”, and it is unique to a particular MS, so it can beused as a universal identifier. In the foregoing description, thesymbolism “xxxxxx” was used to denote the MS identifier, which must becompatible with all iBSs that the MS will roam to in the wirelessnetwork.

[0074] Next, the process by which the MS interacts with a new basestation to convey shadow address information pertaining to the MS isconsidered in overview fashion in FIG. 9. With reference to FIG. 9,there is shown flow diagram 900 for this process; the flow diagramemphasizes those differences over conventional processing brought aboutby the use of a shadow address. The process starts with processing block905 whereby the MS is presumed to be powered up and being served by abase station (referred to as the “old base station” below), as coveredby FIG. 8. The MS continuously monitors, via decision block 910, theincoming signal strength of the old base station to determine if the SNRfalls below a prescribed threshold using the “scanning algorithm”. Ifthe SNR does not fall below a threshold (say 50% of the original SNRratio), the MS continues to monitor the SNR. If the SNR falls below thethreshold, then an operational mode of the MS is turned on so that theMS may communicate with a base station(s). Then via processing 915, theMS scans, using the physical layer, to locate a new base station with ahigher SNR. Next, decision block 920 is invoked to determine whether ornot a new base station has been located. Whenever a new base station hasbeen located, the MS sends a request (including its shadow address andIP address) to associate with the new base station as evidenced byprocessing block 925. The new base station can either accept or rejectthe request to associate. If rejected, the MS continues to scan for ahigher SNR. If accepted, the new base station updates its watch listwith the shadow address and IP address information. The new base stationsends an acknowledgement of receipt of the information, and the MSawaits an acknowledgement from the new base station so as to turn offthe monitor mode (decision block 930). The new base station informs theold base station of the association, via processing block 935; detailsof processing by block 935 from the perspective of the base stations arecovered in FIG. 11. Once soft handoff is complete, then the new basestation will replace the old base station as the serving base station.During soft handoff, the packets being received from the multiple basestations can be used advantageously to determine the true contents ofthe packet from its replicated versions.

[0075] Now with reference to FIG. 10, there is shown flow diagram 1000from the viewpoint a serving iBS upon power-up of a MS within thewireless region served by the iBS. Processing starts with block 1005.Next, decision block 1010 is entered to determine whether or not this isthe first power-up of the MS. If not, then there is no furtherprocessing for this MS. If this is the initial power-up, then block 1015is entered to assign a shadow address to the MS. Then the newly assignedshadow address is inserted into the watch list of the iBS, as perprocessing block 1020. Finally, the shadow address is transmitted to theMS via processing block 1025. Processing ends with block 1030.

[0076] Now with reference to FIG. 11, there is shown flow diagram 1100representative of a candidate base station that is to serve thepowered-up MS as it moves from a serving base station into the overlapof the wireless region of the serving base station and the candidatebase station. Processing starts with block 1105. Next, decision block1110 is entered to determine if there is an approaching MS (known viathe scanning algorithm discussed above). Processing reverts to block1110 if there is no approaching MS. For an approaching MS, viaprocessing block 1115, the shadow address is received from the MS. Thendecision block 1120 is invoked to determine if there is a conflict witha shadow address already in the watch list of the candidate basestation. If there is no conflict, then the original shadow address ishandled by processing block 1125 and is inserted into the watch list ofthe candidate base station. If there is a conflict, processing block1135 is invoked to effect a negotiation between the serving base stationand the candidate base station to determine a suitable replacementshadow address acceptable by both the serving base station and thecandidate base station. Once this negotiation is complete, a new shadowaddress is assigned via processing block 1140, and entered into thewatch list of the candidate base station (as well as replacing the onein the watch list of the serving base station as a result of thenegotiation); also, the candidate base station becomes a new iBS.Processing ends with block 1145.

[0077] Referring now to FIG. 12, there is shown flow diagram 1200representative of the process for deleting a shadow address from thewatch list of a base station once the MS moves outside the range of thatbase station. Processing starts with block 1205. Next, decision block1210 is entered to determine is the MS is leaving the coverage range ofthe base station. If not, there is no further processing. If the MS isleaving the coverage range, then processing block 1215 is entered tosignal that a handoff is to be carried out so that the new base station,differentiated from the old serving base station, will now serve the MS.Once handoff is complete, then processing block 1220 is entered todelete the shadow address from the old base station. Processing endswith block 1225.

[0078] The technique whereby the new iBS obtains shadow addressinformation from the old iBS, rather than from the MS directly, is nowdescribed. The teachings of FIGS. 8-12 can be readily applied to thiscase. It is presumed that the MS is already homing on the old iBS and isnow roaming to the overlap wireless region also served by the new iBS.The MS scans to locate the new iBS. Once the new iBS is located, the MSsends a request to associate with the new iBS; the request includes theMS identifier. The new iBS sends a broadcast message to all other basestations on the subnet to determine which base station has the MSidentifier in its watch list. The old iBS has the MS identifier in itswatch list, so it sends a response to the new iBS with both the IPaddress and the shadow address contained in the old iBS's watch list.Conflicts can be resolved by interchanging messages between the old andnew iBSs, which results in a unique shadow address for the MS now storedin the watch lists of both the new and old iBSs.

[0079] 2. Soft Handoff Across Subnets

[0080] 2.1 Packet Distribution Across Subnets

[0081] With reference to FIG. 13, there is shown system 1300 thatdepicts the scenario for soft handoff across Subnets. In particular, iBSA (1311) is connected to wireline Subnet A (1321), whereas iBS B (1313)is connected to wireline Subnet B (1325). In turn, Subnet A is coupledto router 1322 and Subnet B is coupled to router 1326 (it is possible,without loss of generality, that routers 1322 and 1326 may coalesce intoa single router). Both routers 1322 and 1326 are then coupled to IP corenetwork 1331. Subnet A, Subnet B, and the IP core network may have anyarbitrary network topology. In the arrangement illustrated in FIG. 13,an IP packet sent via iBS A and iBS B to MS 104 during soft handoff, asdepicted by Packet A (1341) and Packet B (1342), respectively,originates from host 1305 coupled to IP core network 1331. Accordingly,when the mobile station moves across IP Subnets, multiple copies of thesame data are to be sent via multiple base stations to the mobilestation (that is, Packet A and Packet B must be identical).

[0082] The manner of achieving the required packet duplication is nowdiscussed for the following heuristic case: a so-called “nearest router”is responsible for IP packet duplication and distribution, namely withreference to FIG. 13, router 1322, since this router is “nearest” to theMS 104 and Subnet A brought about by MS 104 initially homing on iBS A.

[0083] 2.2 Packet Duplication

[0084] Once the soft handoff across IP Subnets A and B starts, that is,as MS 104 migrates from cell 1301 to cell 1302 in handoff region 1317,iBS A, iBS B, and router 1322 exchange information about MS 104. Theinformation is in a form summarized by packet duplication informationwhich, for the case of the nearest router 1322, that is, the routerinitially handling MS 104, is shown in Table 4. TABLE 4 MS Link LayerMS's IP Forwarding IP MS's Shadow Address in Address in Addresses inAddress in Wireless Network Subnet A other Subnets Subnet A xxxxxxIP_(A) IP_(B), . . . . . . MAC₁₀₄ . . . IP₁ IP₂, . . . . . . NIL . . . .. . . . . . . .

[0085] The Forwarding IP Address for a MS can be either the IP addressused by the MS directly to receive IP packets in the new subnet or theIP address of an agent (e.g., a Mobile IP Foreign Agent or an iBS) inthe new subnet that is responsible for intercepting the IP packetsdestined to the MS and then forwarding the packets to the MS.

[0086] The process of filling in, for example, row 1 of Table 4 is asfollows. First, the procedure for assigning a shadow address to MS 104in Subnet A has been discussed with reference to FIG. 8. Then the MSsends information in its watch list to nearest router 1322 so thisrouter can be compiling the duplication table, namely, columns 1, 2, and4 can be filled in. Referring now to flow diagram 1400 in FIG. 14, thetechnique for associating IPB with MS 104 as served by iBS B and theninforming router 1322 of the assignment of IPB for entry into columnthree of Table 4 is depicted.

[0087] The process starts with processing block 1405 whereby the MS ispresumed to be powered up and being served by a base station (referredto as the “old base station” below), as covered by FIG. 8. The MScontinuously monitors, via decision block 1410, the incoming signalstrength of the old base station to determine if the SNR falls below aprescribed threshold using the “scanning algorithm”. If the SNR does notfall below a threshold (say 50% of the original SNR ratio), the MScontinues to monitor the SNR. If the SNR falls below the threshold, thenan operational mode of the MS is turned on so that the MS maycommunicate with a base station(s). Then via processing 1415, the MSscans, using the physical layer, to locate a new base station with ahigher SNR. Next, decision block 1420 is invoked to determine whether ornot a new base station has been located. Whenever a new base station hasbeen located, the MS sends a request (including its MS identifier andits IPA address) to associate with the new base station as evidenced byprocessing block 1425. The new base station can either accept or rejectthe request to associate. If rejected, the MS continues to scan for ahigher SNR. If accepted, the new base station (iBS B) sends anacknowledgement that it will associate with the MS. The MS awaits anacknowledgement from iBS B so that the MS may turn off its monitor mode(decision block 1430). The MS and iBS B exchange a sequence of messagesusing, for example, the Dynamic Host Configuration Protocol, to assignthe new IP address IPB to the MS for use in Subnet B, as evidence byprocessing block 1435. Then the MS sends a message as part of its normalinterchange with iBS A to inform iBS A of the new IP_(B) address, as perprocessing block 1440. Finally, the iBS A sends a message containing thenew address IPB to the nearest router (1322), as per processing block1445, for completing the remaining entry in the Packet Duplication Table4, namely, column three. Processing is ended by block 1450.

[0088] Once soft handoff is complete, then the new base station willreplace the old base station as the serving base station. During softhandoff, the packets being received from the multiple base stations canbe used advantageously to determine the true contents of the packet fromits replicated versions.

[0089] It is possible that more than one “new” candidate base stationmay be located during the process of “scanning” for a new base stationor base stations. Each new base station independently follows a processas elaborated upon in the foregoing for the interaction between iBS Aand iBS B. The interaction of only iBS A and iBS B has been discussedfor the sake of specificity but without loss of generality.

[0090] Now, for any incoming IP layer packet arriving from host 1305,router 1322 routes, via iBS A, the original Packet A destined for IPaddress IPA of MS 104 using its standard routing procedure. In addition,router 1322 duplicates the packet and distributes the duplicate to MS104 as Packet B via iBS B. In general, the procedure is that when anearest router receives a packet destined to the IP addresses in firstcolumn of Table 4, it duplicates the packet and sends the duplicates tothe IP address(es) in the third column of Table 4. Therefore multiplestreams will be sent to all base stations involved in soft handoff.

[0091] In some situations, a nearest router may need to respond to theARP REQUEST to receive the IP packets destined for mobile 104. Thereforethe shadow address of MS 104 is maintained in second column of Table 4.Also, if an iBS connects to multiple nearest routers, only one of thenearest routers is chosen to store the shadow address of MS 104. Otherswill simply put NIL in the field, as exemplified by the second row ofTable 4. Similarly, signaling is performed in iBSs A and B and thenearest router 1322 when soft handoff is completed, so the entry of themobile station in a Packet Duplication table will be deleted. Suchsignaling can be done along with the signaling used by the mobilestation to normally perform soft handoff.

EXAMPLE 1

[0092] By way of specificity to summarize the procedure step-by-step,consider the arrangement of FIG. 13 wherein Packet A is sent fromcorrespondent host 1305 attached to IP core network 1331, that is, thepacket has IP destination address IPA and is sent from “outside” SubnetA. Since Packet A with destination address IPA is sent outside Subnet A,it is eventually routed to router 1322. Once router 1322 receives PacketA, it checks its Duplication Table. Packet A therefore will beduplicated with IP destination address of IPB as depicted in the thirdcolumn of Table 4, and this duplicated packet is be routed to MS 104 viaiBS B. Besides, Packet A is routed to MS 104 via iBS A as a standardpacket.

[0093] If there are multiple nearest routers an iBS connects to, onlyone of them receives the packet sent from host 1305. Therefore only onenearest router will duplicate and distribute the packet.

[0094] As outlined above, each time a mobile station moves to a newSubnet, it must acquire a private or public IP address from a server(e.g. DHCP server or Foreign Agent) for that specific Subnet. This ispart of the normal registration and configuration. However, which IPaddress correspondent host 1305 should use to reach the mobile stationdepends on how IP-layer mobility is supported. If, for example, basicMobile IPv4 is employed, host 1305 always uses the home address of themobile station. The Forwarding IP Address, IP_(B), for the MS in the newcell would be the new care-of address the MS obtains for receivingpackets in the new subnet. The normal Mobile IPv4 Home Agent processdirects a packet to the MS's care-of address currently registered withthe Home Agent. In this example, the MS can delay the Mobile IPv4address binding operation for its new care-of address IP_(B) until softhandoff is completed so that the Mobile IPv4 Home Agent can continue todirect packets destined to the MS to the old base station during thehandoff. Router 1322 will then duplicate the packet and forward a copyto the new base station as described above. Upon completion of softhandoff, the MS will perform Mobile IP address binding operation for itscare-of address to be used in the new cell so that later packets will bedirected to this new care-of address. To reduce packet loss during theswitch over from old IP address to the new IP address, removal of theDuplication Table in Router 1322 may be delayed for a pre-determined orrandom time after the completion of soft handoff so that packets alreadysent to the old cell can continued to be forwarded by Router 1322 to thenew cell even after the MS loses its radio connection with the IBS A.

EXAMPLE 2

[0095] For this example, suppose for the moment that host 1305 isconnected to Subnet A, that is, Packet A is sent from “inside” Subnet A,so that both router 1322 and iBS A respond to an ARP REQUEST with themobile station's shadow address. Therefore, Packet A eventually arrivesat both iBS A and router 1322. The one arriving at router 1322 isforwarded to the IP address(es) in third column of the Table 4 stored inrouter 1322. Since this packet arriving at router 1322 is due to theentry in the Duplication Table rather than the normal routing table,router 1322 does not perform normal routing so the packet will not besent to iBS A again. In this example, only one of the nearest routersmaintains the shadow address in its Duplication Table, so that only oneof them duplicates and distributes a packet.

[0096] 2.3 Distribution of Same Data in Multiple Streams

[0097] When the nearest router sends out the duplicated IP packets,these packets have different IP addresses of the mobile station so theycan be routed to different base stations. To effect soft handoff,packets must be exactly the same including any field in the header socombining of fields can be done in signal level by the mobile station.Packets duplicated and distributed from the nearest routers however aredifferent in their destination IP addresses.

[0098] However, all the other fields other than the IP destinationaddress are same when the nearest router duplicated the packets. Asdescribed in Section 1, the base stations perform signaling and maintaina Watch List for mobile stations involved in the soft handoff process.Base stations therefore know which mobile stations are currently in theprocess of soft handoff across Subnets. The new base station thenchanges the IP destination address of the packet for the mobile stationin the Watch Lists of the base station to the mobile station's old IPaddress (IP_A). But instead of broadcasting these IP packets, the basestations will further encapsulate the IP packets to link layer frameswith the link layer address in the Watch List as the destinationaddress. These link layer frames will be sent from base stations to themobile over the air interface without broadcasting; upon receipt by themobile station, the link layer information is stripped from the frame,leaving only the packet with the generic broadcast address which isidentical for all packets. The involved mobile station therefore willreceive exactly same data from multiple base stations.

[0099] 2.4 Packet Selection in Reverse Link

[0100] The nearest router described above for packet distribution couldbe the point for packet selection as well, that is, the process ofselecting one of the packets arriving from the MS via a correspondingplurality of base stations as the propagated pakcet.

[0101] For soft handoff in circuit cellular networks, the Nearest Routerreceives RLP (Radio Link Protocol) frames from multiple base stations.In addition to the payload, each RLP frame also comprises of SIR (SignalInterference Ratio), Frame Quality Indicator (FQI), Symbol Error Rate(SER), and so forth. Based on this information, one frame is singled outas the “best” frame for further distribution in the network. To preservesuch layer-2 information, the iBSs encapsulate layer-2 frames to IPpackets, then send them to the Nearest Router, which then decapsulatesthe IP packets, selects one layer-2 frame, and assembles final IPpackets. The restored packets are then routed to the correspondent host(1305) by the Nearest Router. This approach allows the iBSs to performsoft handoff in reverse link in layer-2 as that in today's cellularnetworks. The only added function in iBSs is to encapsulate the RLPframe to IP packets. The Nearest Router, however, will need to performdecapsulation, selection, and IP assembly.

[0102] An alternative approach is to generate an IP packet when the iBSreceives a RLP frame. The iBS generates an IP packet with the payload ofthe RLP frame and the decision criteria. Once the Nearest Routerreceives the RLP frame, it can select a packet based on IP payload, thenassemble the original IP packet sent by MS and route it to thecorrespondent host.

[0103] Packet selection in the reverse direction has been described withrespect to soft handoff across subnets. It is readily contemplated thatan analogous description applies to packet selection in the reversedirection for soft handoff within a subnet.

[0104] 3. Data Content Synchronization

[0105] One potential way to achieve data content synchronization at theMS is to have all iBSs transmit copies of the same packet to the mobilestation at precisely the same time. However, scheduling the precisetiming for simultaneous transmissions of IP packets on different IPdevices (in this case, iBSs) is very difficult to implement in a real IPnetwork.

[0106] This Section describes a new IP-layer procedure, referred to asthe “Fluid Synchronization” method, performed by the iBSs to ensure thatthe data arriving at the MS at the same time from multiple iBSs arecopies of the same data. The method is an IP-layer procedure and istherefore independent of the link layer protocols used in the radiosystem. The procedure is performed by iBSs rather than by the MS, whichavoids any modification to the MS.

[0107] Rather than trying to schedule the precise timing forsimultaneous IP packet transmissions on multiple iBSs, the methodologyensures that the streams of layer-2 data blocks sent by multiple iBSs tothe MS are “matchable streams”. Matchable streams are streams of layer-2blocks (or more precisely, the physical layer data resulting from theseblocks) that can be correctly matched and combined by the MS usingtoday's radio technologies (e.g., a RAKE receiver as discussed in thereference by V.K Garg, entitled “IS-95 CDMA and cdma 2000:Cellular/PCSSystems Implementation”, pp. 60-62, published by Prentice-Hall, 2000).

[0108] Suppose that the streams of IP packets sent by different iBSs tothe MS have either no gaps (i.e., no missing IP packets) or identicalgaps. Then, the layer-2 data block streams from the iBSs to the MS willbe matchable if, for any k, the k^(th) layer-2 data block sent by bothiBSs to the MS contains the same amount of payload (i.e., have the samelength). The matching layer-2 data blocks (i.e., data blocks that arecopies of the same data) from different iBSs do not have to arrive atthe mobile at precisely the same time. The mobile's radio system cansynchronize these data blocks using today's radio channelsynchronization techniques, as long as the delay jitters are notexcessively large, which usually is one time slot length of a frame.

[0109] It is also important to note that generating matchable streams oflayer-2 data blocks does not require each iBS to send copies of the sameIP packet to the layer-2 protocol at precisely the same time fordelivery to the MS. Furthermore, matchable streams of layer-2 datablocks can be generated by performing only IP-layer processing on theiBSs alone.

[0110]FIG. 15 illustrates how matchable streams of layer-2 data blockscan be generated when the IP packets are sent by different iBSs to thelayer-2 protocol on their radio interfaces at different times fordelivery to the MS. With reference to FIG. 15, there is shown a streamof numbered packets, designated “1” (1511), “2”, “3”, “4”, “5”, “6”, andso forth, arriving at, for example, iBS A of FIG. 13. Similarly, thesame stream of packets arrives at iBS B, wherein packet 1521 is thefirst packet in the stream. Note that the packets arrive at therespective iBSs at different times (time line 1531-1 is used toreference packets for iBS A, whereas replicated time line 1531-2 is usedfor packets arriving at iBS B). IP packets are sent to the link layerfor delivery over-the-air to the MS at the times shown by the downwardarrows on the respective time lines; for example, packet 1511 istransmitted at the time shown by arrow 1512, and packet 1521 istransmitted at the time shown by arrow 1522. The over-the-air link layerreceives the packets as data blocks and fills the data blocks into linklayer frames. The over-the-air link layer frames corresponding to iBS Aare shown by the stream of frames starting with 1513, 1514, and soforth. Similarly, the over-the-air link layer frames corresponding toiBS B are shown by the stream of frames starting with 1523, 1524, and soforth. Frames 1513 and 1523 are blank, and they are shown primarily todemonstrate that there is a random delay (1532) between the two streamsof frames. As long as the random delay is within the synchronizationcapability of the receiver technique, fluid synchronization can beeffected. The “sideways” arrows, such as arrow 1515, depict when the iBSA IP packets sent to the link layer for delivery over-the-air have beenfully processed and are encapsulated into frames. Thus, frame 1514encapsulates the data blocks derived from packets “1” and “2” from iBSA. Similarly, the next frame encapsulates data from packets “2” and “3”.Because the data block associated with packet “5” undergoes asignificant delay in delivery, the data block for packet “5” is notready for encapsulation until the fifth frame. Moreover, this data blockis too long for a single frame, so it is used to partially fill the nextsucceeding frame, along with data from packet “6”. Finally, anotherframe is needed to complete delivery of packet “6” because of itslength.

[0111] Similarly, the “sideways” arrows, such as arrow 1525, depict whenthe iBS B IP packets sent to the link layer for delivery over-the-airhave been fully processed and are encapsulated into frames. Thus, frame1524 encapsulates the data blocks derived from packets “1” and “2” fromiBS B. Similarly, the next frame encapsulates data from packets “2” and“3”. Because the data block associated with packet “5” undergoes asignificant delay in delivery, the data block for packet “5” is notready for encapsulation until the fifth frame. Moreover, this data blockis too long for a single frame, so it is used to partially fill the nextsucceeding frame, along with data from packet “6”. Finally, anotherframe is needed to complete delivery of packet “6” because of itslength.

[0112] Based on the observations described above, a BasicSynchronization Procedure (BSP) is as follows (the Radio Link Protocol(RLP) is used as an exemplary radio layer-2 protocol in the followingdiscussions). Starting from the delivery of the same IP packet to themobile, each iBS will

[0113] 1) Use RLP frames of identical length

[0114] 2) Deliver only fully filled RLP frames to the MS unless

[0115] a) a timer T_(p) expires, or

[0116] b) instructed by the upper layer (i.e., the IP layer) to send thecurrent data.

[0117] In real networks, several events may cause a loss of data contentsynchronization when the above method is used. For example, gaps mayrandomly occur in the IP packet streams sent by different iBSs to themobile. Also, when timer T_(p) times out or when the IP layers ondifferent iBSs instruct their layer 2 to send the current availabledata, the resulting layer-2 data blocks from different iBSs may notcontain an identical amount of payload.

[0118] To correct for these events, a data content re-synchronizationprocedure is described that can quickly bring the multiple layer-2 datablock streams from different iBSs back to synchronization when loss ofdata content synchronization occurs. The foundational principle is thatthe iBS which detects (or suspects) a loss of data contentsynchronization will negotiate with the other iBSs to restart the BSPprocedure from a new IP packet.

[0119] This following describes the data content re-synchronizationprocedure using packet gaps as an exemplary cause of loss of datacontent synchronization. To help iBSs detect gaps in IP packet streams,the source or the entity responsible for packet distribution can numberthe packets (e.g., using the 16-bit identification field or an optionalfield in the IP header) and increment the packet stream number by oneeach time an IP packet is sent.

[0120] The depiction of FIG. 16 is a pictorial representation of theresults to be determined by the re-synchronization procedure. Inparticular, FIG. 16 illustrates two streams of frames sent to the MSfrom iBS A and iBS B, namely, the stream from iBS A encapsulatingpackets 1611, . . . , 1612, and the stream from iBS B encapsulatingpackets 1621, . . . , 1622, . . . , 1623. The frames from iBS B aredelayed relative to the frames from iBS A, as already pointed out inFIG. 15. In the depiction of FIG. 16, the frame containing packet “3”from iBS A has been “lost” in the over-the-air delivery from iBS A tothe MS. Data content resynchronization is regained at the RLP frames1612 and 1623, respectively, for iBS A and iBS B, based upon the abovedata content synchronization procedure now discussed in steps (a)-(f)below.

[0121] Suppose that iBS A detects a gap between packet k and packet m(m>k) in the stream of IP packets destined to the MS. That is, iBS A hasreceived packets k and m but has not received any packet between packetsk and m. iBS A will initiate the following data contentre-synchronization procedure, discussed with reference to flow diagram1700 of FIG. 17 (as a shorthand, a number x in a layer-2 frame indicatesthat the layer-2 frame contains data from the IP packet with streamnumber x):

[0122] (a) 1705: iBS A requests iBS B to re-start the BSP procedure froma packet q (q≧m).

[0123] (b) 1710: iBS A immediately sends to the MS all the packets ithas received before packet q without enforcing the BSP rules and haltsthe delivery of packet q and the packets arrived after packet q.

[0124] (c) 1715: determine if iBS B can (or has a high level ofconfidence that it can) re-start data synchronization as requested byiBS A (e.g., when iBS B has received packet q and has not yet sent it tothe MS, or has not yet received packet q).

[0125] (d) if so, iBS B will positively acknowledge iBS A's request(1720). Then, iBS B will immediately send to the MS all the packets itreceived before packet q without enforcing the BSP rules (1725). iBS Bwill then restart the BSP procedure from packet q (1730). In otherwords, layer-2 transmission of packet q will start from the beginning ofa new layer-2 frame after the packets before q have been delivered.Further, starting from packet q, layer-2 transmission will follow theBSP rules.

[0126] (d) 1735: upon receiving positive acknowledge from iBS B, IBS Awill restart the BSP procedure from packet q.

[0127] (e) if iBS B cannot re-start re-synchronization as requested byiBS A (e.g., iBS B may have already sent packet q to the MS), iBS B willselect a new packet r after packet q (r>q) and requests iBS A to startre-synchronization at packet r (1740).

[0128] (f) both iBS A and iBS B start BSP procedure commencing withpacket r (1745).

[0129] The re-synchronization procedure described above can be used tore-gain data content synchronization when loss of data contentsynchronization is caused by other events besides gaps in IP packetstreams. If, for example, T_(p) on iBS B expires before a RLP frame isfully filled, iBS B will send the partially filled frame to the MS.However, this may lead to loss of data content synchronization. Tore-gain data content synchronization, iBS B can request iBS A tore-start the BSP procedure from a new packet. To reduce the impact ofloss of data content synchronization caused by unexpected events, theiBSs currently involved in soft handoff may periodically re-start thedata content re-synchronization procedure.

[0130] 4. Smooth Handoff

[0131] This Section discusses how to leverage the Shadow Addressesmaintained in each base station to achieve “smooth handoff”. Smoothhandoff means that the mobile station still can transmit and receivepackets while it is performing handoff. Ideally there will be no delayand packet loss in smooth handoff. Again, a macro-diversity system isassumed, that is, the system is such that that a mobile station iscapable of transmitting and receiving data from multiple base stationsat the same time. Although smooth handoff in a macro-diversity system isfeasible in current circuit-based centralized cellular systems, thefocus of this Section is on packet-based IP networks in which there isno central controller. In addition, the subject matter in accordancewith the present invention has the following unique features:

[0132] (a) the same algorithms and table can be used for both link- andnetwork- layer handoffs. The base station does not need to distinguishthe type of handoff, and does not need to run two handoff algorithms.This makes the IP-based base station efficient and also reduces thecost.

[0133] (b) the same algorithms and table can be used for mobile stationsserved by multiple base stations either on same or different IP subnet.

[0134] (c) no signaling at or above the IP layer is required.

[0135] (d) a mobile station does not have to use an additional IPaddress.

[0136] (e) no modification to the mobile station is required. Basestations maintain the necessary table, cache the shadow addresses, andperform extra techniques for handoff.

[0137] (f) the smooth handoff technique scales well for large networks.

[0138] 4.1 Smooth Handoff within a Subnet

[0139] Base stations perform the algorithms in Sections 1.1, 1.3 and 1.5to assign and insert a shadow address in the Watch Lists for the mobilestation. Base stations then respond to an ARP REQUEST when there is anIP packet destined to the mobile station. Since the base stationsinvolving in the smooth handoff have the same shadow address for themobile station, the mobile station will receive the IP packets from atleast one base station. Therefore smooth handoff can be achieved. Theentry of the mobile station in the old base station will be deleted oncethe handoff is done. The mobile station then will receive packets onlyfrom one base station.

[0140] 4.2 Smooth Handoff Across Subnets

[0141] For handoff across different subnets, base stations again performthe same algorithms in Sections 1.1, 1.3 and 1.5. The shadow addressesused by the same mobile station in cells belonging to different IPsubnets may be the same or different. Depending on specific IP-layermobility management methods, IP packets may be sent to a single ormultiple base stations. In particular, if soft handoff in the IP layeris deployed, IP packets will be sent to multiple base stations. Smoothhandoff can be achieved using the same method described in the Section4.1. If soft handoff is not deployed in the IP layer, the IP packetswill be destined to only one base station (i.e., either the new or theold base station). Either the new or the old base station will be ableto correctly respond to the ARP REQUEST from any other network device(e.g., an IP router or another iBS) that wants to send IP packets to it.This is because either one of the base stations will already have themobile station's shadow address in its Watch List. Therefore, the IPpackets can reach the mobile station from either one of the basestations. Base stations do not need to do any extra signaling with otherbase stations in either the link- or the network-layer for carrying outhandoff. Furthermore, only one handoff is needed when mobile stationmoves across IP subnets. Thus, smooth handoff is achieved easily in bothlink- and network-layers.

[0142] Also, by way of reiteration, each time when the mobile stationmoves to a new subnet, it must acquire a private or public IP addressfrom a server (e.g. DHCP server or Foreign Agent) for that specificsubnet. This is part of the registration and configuration. Which IPaddress the CH should use to reach the mobile station depends on howlocation update is performed. If basic Mobile IPv4 is employed, forexample, CH always uses the home address of the mobile station. Thenormal Home Agent process directs a packet to old (or home) IP addressbefore handoff, that is, registration of new IP address with the HomeAgent is delayed until soft handoff is completed.

[0143] In some cases, the mobile station may perform smooth handoff withmultiple base stations. Not all of these cells may be on the same IPsubnet. The algorithms still apply in this case and smooth handoff canbe achieved as well.

[0144] Although the present invention have been shown and described indetail herein, those skilled in the art can readily devise many othervaried embodiments that still incorporate these teachings. Thus, theprevious description merely illustrates the principles of the invention.It will thus be appreciated that those with ordinary skill in the artwill be able to devise various arrangements which, although notexplicitly described or shown herein, embody principles of the inventionand are included within its spirit and scope. Furthermore, all examplesand conditional language recited herein are principally intendedexpressly to be only for pedagogical purposes to aid the reader inunderstanding the principles of the invention and the conceptscontributed by the inventor to furthering the art, and are to beconstrued as being without limitation to such specifically recitedexamples and conditions. Moreover, all statements herein recitingprinciples, aspects, and embodiments of the invention, as well asspecific examples thereof, are intended to encompass both structural andfunctional equivalents thereof. Additionally, it is intended that suchequivalents include both currently known equivalents as well asequivalents developed in the future, that is, any elements developedthat perform the function, regardless of structure.

[0145] In addition, it will be appreciated by those with ordinary skillin the art that the block diagrams herein represent conceptual views ofillustrative circuitry embodying the principles of the invention.

What is claimed is:
 1. A method for carrying out soft handoff of amobile station from a first base station to a second base station bothserved by a wireline subnet having a link layer different than the linklayer of the wireless network serving the mobile station, the methodcomprising storing a shadow address in the first base station and thesecond base station, the shadow address corresponding to the mobilestation and having a format compatible with the link layer of thewireline subnet, transmitting a frame containing the packet from thesending device over the wireline subnet using the shadow address as thelink layer destination address of the packet, and concurrentlyprocessing the frame in the mobile station as received from the firstbase station and the second base station.
 2. The method as recited inclaim 1 wherein the storing includes assigning the shadow address by thefirst base station.
 3. The method as recited in claim 2 wherein thetransmitting includes communicating the shadow address from at least oneof the base stations to the sending device in response to an addressresolution request by the sending device.
 4. The method as recited inclaim 1 further comprising, after the transmitting, simultaneouslysending the packet, using a link layer frame compatible with the linklayer of the wireless network, from both the first base station and thesecond base station to the mobile station.
 5. The method as recited inclaim 1 wherein the mobile station has an IP layer address and thestoring includes storing the IP layer address, the shadow address, andthe wireless link layer address as entries in a watch list for themobile station.
 6. The method as recited in claim 1 further comprising,prior to the storing, sending the shadow address from the first basestation to the mobile station and storing the shadow address in themobile station.
 7. The method as recited in claim 6 further comprising,after the sending, transmitting the shadow address to the second basestation from the mobile station.
 8. The method as recited in claim 6further comprising, after the sending, transmitting the shadow addressto the second base station from the mobile station as part of a standardmessage to register the mobile station with the second base stationduring roaming.
 9. A method for servicing a mobile station homing on afirst base station and roaming to a second base station both served by awireline subnet having a link layer different than the link layer of thewireless network serving the mobile station, the method comprisingassigning a shadow address to a mobile station by the first basestation, the shadow address having the same format as the link layeraddress of the subnet, sending a request from the mobile station toassociate with the second base station, the request including the shadowaddress, and associating the mobile station with the second base stationwith reference to the shadow address.
 10. The method as recited in claim9 further comprising, after the sending, negotiating between the firstbase station and the second base station a replacement shadow address ifthe shadow address assigned by the first base station conflicts with apre-existing shadow address handled by the second base station.
 11. Amethod for servicing a mobile station homing on a first base station androaming to a second base station both served by a wireline subnet havinga link layer different than the link layer of the wireless networkserving the mobile station, the method comprising assigning a shadowaddress to a mobile station by the first base station, the shadowaddress having the same format as the link layer address of the subnet,sending a request from the mobile station to associate with the secondbase station, sending a message over the subnet from the second basestation to locate the first base station having the assigned shadowaddress, and responding to the message by the first base station withthe shadow address.
 12. The method as recited in claim 11 furthercomprising, after the sending, negotiating between the first basestation and the second base station a replacement shadow address if theshadow address assigned by the first base station conflicts with apre-existing shadow address handled by the second base station.
 13. Amethod for carrying out IP layer soft handoff of a mobile station from afirst base station to a second base station both served by a wirelinesubnet having a link layer different than the link layer of the wirelessnetwork serving the mobile station, the method comprising assigning ashadow address to the mobile station, the shadow address correspondingto the mobile station and having a format compatible with the link layerof the wireline subnet, storing the shadow address in both the firstbase station and the second base station, communicating the shadowaddress from at least one of the stations to the sending device inresponse to a address resolution request by the sending device,transmitting a frame containing the packet from the sending device overthe wireline subnet to both the first base station and the second basestation using the shadow address as the link layer destination addressof the packet, propagating the packet from the first base station to themobile station using the IP layer of the wireless network, andconcurrently propagating the packet from the second base station usingthe IP layer of the wireless network, and concurrently processing thepacket as receive from the first base station and the packet as receivedfrom the second base station in the mobile station.
 14. The method asrecited in claim 13 wherein the mobile station has an IP layer addressand the storing includes storing the IP layer address, the shadowaddress, and the wireless link layer address as entries in a watch listfor the mobile station.
 15. The method as recited in claim 14 whereinthe address resolution request includes the IP layer address of themobile station and the communicating includes looking up the shadowaddress in the watch list corresponding to the IP layer address of themobile station and sending the shadow address in response to the addressresolution request.
 16. The method as recited in claim 13 wherein thepropagating the packet from the first base station includes removing thepacket from the wireline frame, passing the packet to the IP layer ofthe first base station, encapsulating the packet as a link layerwireless frame, and propagating the link layer wireless frame over aradio channel coupling the first base station with the mobile station.17. The method as recited in claim 13 wherein the propagating the packetfrom the second base station includes removing the packet from thewireline frame, passing the packet to the IP layer of the second basestation, encapsulating the packet as a link layer wireless frame, andpropagating the link layer wireless frame over a radio channel couplingthe second base station with the mobile station.
 18. The method asrecited in claim 13 wherein the propagating the packet from the firstbase station includes removing the packet from the wireline frame,passing the packet to the IP layer of the first base station,encapsulating the packet as a link layer wireless frame, and propagatingthe link layer wireless frame over a radio channel coupling the firstbase station with the mobile station, and wherein the propagating thepacket from the second base station includes removing the packet fromthe wireline frame, passing the packet to the IP layer of the secondbase station, encapsulating the packet as a link layer wireless frame,and propagating the link layer wireless frame over a radio channelcoupling the second base station with the mobile station.
 19. Circuitryfor carrying out soft handoff of a mobile station from a first basestation to a second base station both served by a wireline subnet havinga link layer different than the link layer of the wireless networkserving the mobile station, the circuitry comprising a storage devicefor storing a shadow address in the first base station and the secondbase station, the shadow address corresponding to the mobile station andhaving a format compatible with the link layer of the wireline subnet, areceiver for receiving a frame containing the packet transmitted fromthe sending device over the wireline subnet to both the first basestation and the second base station using the shadow address as the linklayer destination address of the packet, and a processor forconcurrently processing the frame as receive from the first base stationand the frame as received from the second base station in the mobilestation.